Deliverable: Transition Architecture
Purpose
A Transition Architecture shows the enterprise at incremental states reflecting periods of transition that sit between the Baseline and Target Architectures. Transition Architectures are used to allow for individual work packages and projects to be grouped into managed portfolios and programs, illustrating the business value at each stage.
Relationships
Main Description

Typical contents of a Transition Architecture are:

  • Opportunity portfolio:
    • Consolidated gaps, solutions, and dependency assessment
    • Opportunity description
    • Benefit assessment
    • Capabilities and capability increments
    • Interoperability and co-existence requirements
  • Work package portfolio:
    • Work package description (name, description, objectives, deliverables)
    • Functional requirements
    • Dependencies
    • Relationship to opportunity
    • Relationship to Architecture Definition Document and Architecture Requirements Specification
  • Milestone and milestone Transition Architectures:
    • Definition of transition states
    • Business Architecture for each transition state
    • Data Architecture for each transition state
    • Application Architecture for each transition state
    • Technology Architecture for each transition state
  • Implementation Factor Deduction matrix, including:
    • Risks
    • Issues
    • Assumptions
    • Dependencies
    • Actions
  • Consolidated Gaps, Solutions, and Dependencies matrix, including:
    • Architecture domain
    • Gap
    • Potential solutions
    • Dependencies
Deliverable Properties